Introduction

Over time, the tempcache will be filled with various renditions of documents, including both the original rendition of documents and converted renditions of documents. Both PCC for SharePoint and PCC will write to this folder, but neither is responsible for cleaning up old files in the folder. Tempcache cleanup is the process of maintaining the content of this folder.

Implementing tempcache cleanup requires defining a retention policy. The retention policy can define under what conditions files are kept in the tempcache and what conditions they are removed from the tempcache. A retention policy should balance performance, security, and storage considerations:

• Performance considerations essentially come down to the fact that if a document rendition is already in the tempcache, then no additional processing needs to be done to obtain the document.

• Security considerations are based around limiting the risk of unauthorized access to the tempcache. If files are held longer in the tempcache, then there is potentially more data exposed on unauthorized access to the tempcache.

• Storage considerations are based on the cost to store data.

A basic tempcache cleanup policy and implementation is defined below. These may be followed or you can choose a different implementation that better meets your needs:

Retention Policy

• All documents will be removed from the tempcache after 24 hours, with a 1 hour grace period.

Cleanup Implementation

The Prizm Cache Manager tool can be used to implement the retention policy. This tool ships and installs with Prizm Content Connect and is located in the "CacheManager" folder of the Prizm installation directory, for example: C:\Prizm\CacheManager.

To implement the given retention policy with the Prizm Cache Manager, use the following settings:

• Directory: <your tempcache folder>
• Extensions: *.*
• Size limit: 10 GB
• Delete files older than: 24 hours
• Run cleanup every: 1 hour